HyperLib 1997 Winter - Disc 1/HYPERLIB-1997-Winter-CD1.ISO.7z/HYPERLIB-1997-Winter-CD1.ISO/オンラインウェア/UTIL/Menu Events 1.3 folder.sit/Menu Events 1.3 folder/Menu Events 1.3/Menu Events Help.rsrc/STR#_1030.txt

Text File | 1996-03-06 | 7KB | 319 lines

窶｢  Initial AWOL Utilities 1.0.1 release.□

□□1.0.1 (December 31, 1993)□

□

if it received a Menu event from a remote sender.□

窶｢  Fixed bug which sent the target application into a notification wait state

□□1.0.2 (January 11, 1994)□

□

窶｢  Added 窶廴enu Events 'aete'窶 resource file.□

□□1.0.3 (January 19, 1994)□

□

one second to let the user release the key(s).□

If the Help or Command-? key is pressed, the extension will delay up to

窶｢  If the Shift key is pressed on startup, the extension will not be loaded.

□□1.0.4 (January 30, 1994)□

□

mouse-down events when they become active.□

窶｢  Improved compatibility with At Ease and other applications which flush

□□1.0.5 (February 6, 1994)□

□

窶｢  Added protection against loading duplicate copies of the extension.□

□□1.0.6 (February 27, 1994)□

□

print it when the help server is absent.□

窶｢  Menu Events Help presents a useful message if the user tries to open or

□□1.0.7 (March 13, 1994)□

□

窶｢  Documented that Menu Events works with Finder 7.1.2.□

窶｢  Public AWOL Utilities 1.1 release.□

□□1.1 (March 28, 1994)□

□

Script窶 in place of 窶廴enu Events 'aete'窶 resource file.□

窶｢  Added 窶廴enu Events Scripting Addition窶 and 窶廴enu Events Sample

□□1.1.1 (April 11, 1994)□

□

□□non-standard menu definition procedures.□

□□improve compatibility with target applications which use slightly

□□keyMenuMDEFID parameter in the reply to the Query Menu List event, to

□□窶｢  Removed the nonStandardMenuErr (-21004) code in favor of the new

□□the Select Menu Item event.□

□□窶｢  Added support for modifier keys (Shift, Control, Option, Command) in

□□menu item and the Caps Lock key is down.□

□□applications to send themselves Menu events when the user selects a

□□窶｢  Added support for script recording by forcing high-level-event-aware

□□1.1.2 (April 19, 1994)□

□

窶｢  No revisions.□

窶｢  Public AWOL Utilities 1.2 release.□

□□1.2 (October 17, 1994)□

□

string parameters.□

窶｢  Rewrote 窶廴enu Events Sample Script窶 to make use of the new optional

that errors are reported sensibly in AppleScript alerts.□

窶｢  Moved the error codes from the -21000 range to the -15950 range, so

occurs.□

窶｢  Added an error string parameter to the reply event when an error

□□application send itself a Menu event to invite recording.□

□□to a simple Apple event recording action, instead of having the target

□□窶｢  Changed the response to a menu selection with the Caps Lock key down

□□menu in response to a Query Menu or Select Menu Item event.□

□□force the application to update its menus, before reading the contents of a

□□窶｢  Improved application compatibility by simulating a menu bar click, to

□□the Query Menu event.□

□□窶｢  Added support for modifier keys (Shift, Control, Option, Command) in

□□returned if the numeric and string parameters do not match.□

□□with or without the corresponding numeric ID parameters.  An error is

□□窶｢  Allowed menus and menu items to be specified using string parameters,

窶｢  Public AWOL Utilities 1.3 release.□

□□1.3 (March 6, 1996)□

□□□□

□□□□□

□□□it describes.□

□□□Click on any underlined item in this listing to read more about the revision

□

□

□□□□□□□ﾃ･□□□Revision History□

□□□□□□ﾃｲ□

□□□□□□ﾃｲ

□

□□□□□

□

□

hospitality at the MacScripting mailing list.□

James Edward Davis, and Leonard Rosenthol, and to Fred Terry for his

including Ken Linger, Chris Reynolds, Michele Marques, Chris Kaltwasser,

Special thanks to the many fine people who beta-tested this software,

□

□□□□□

folks like me such odd ideas.□

Support who put together those clever little code snippets which give

Thanks to C.K. Haun and the other folks at Apple Developer Technical

□

□

□□□□□□□ﾃ･□□□Acknowledgements□

□□□□□□4□

□□□□□□4

□

□□□□□

□

□

□□□□□

the Menu Events extension or how it was programmed.□

Write to the author at the above address if you want to know more about

□

□

□□□□□□□ﾃ･□□□Programmer Notes□

□□□□□□窶“□

□□□□□□窶“

□

□□□□□

□

□

may hang.□

code which should not be called when in the background, the application

the menu action causes a call to the Standard File Manager or any other

Apple event to the help server, causing it to return to the background.  If

event窶冱 user interaction ends when the receiving application sends an

problems may occur with the application.  The problem is that the Menu

before performing the menu action, and if the help server is running,

send a Menu event to an application which does a casual help display

A known conflict exists between Menu Events and Help on Wheels.  If you

□

Menu Events from activating the target application.□

true if the target machine is already showing a modal dialog, preventing

then Query Menu and Select Menu Item events will time out.  The same is

package which would present a modal dialog in response to a mouse click,

If the target machine is under the influence of a screen saver or security

□

box.  It is then up to the local user to operate the controls.□

('窶ｦ') character, you can bet that the application will post a dialog or alert

response to the menu action.  If the menu item text ends in an ellipsis

operate dialogs and alerts which the target application may post in

Another limitation you should know about is that Menu Events can窶冲

□

same machine the right to request user interaction, which is the default.□

event handlers can get a crack at it.  Don窶冲 deny other programs on the

wildcard event handler, return errAEEventNotHandled, so that system

Apple event, and dispatch it as such.  If an unknown event reaches your

Apple event.  Assume that any high-level event you don窶冲 recognize is an

high-level-event-aware.  Always be ready to accept and dispatch an

as you follow the practices suggested in Apple documentation, namely:  Be

controlling.  Certainly, anything you write yourself is a candidate, as long

The only way to know for sure is to try the ones you are interested in

□

□□□□□

therefore should not be targeted.□

binding their own event handlers over all Apple event classes, and

Microsoft applications handle Apple events in a non-standard fashion,

replied to, and the send will time out.  ResEdit 2.1.1 is similar.  Some

only respects events of known types.  Any other high-level event is not

Macintosh (version 7.1.2).  It is not truly an Apple event server, and it

prime example is any version of Finder which predates the Power

Some applications refuse to submit to the trickery of Menu Events.  The

□

□

□□□□□□□ﾃ･□□□Limitations□

□□□□□□l□

□□□□□□l

□

□□□□□